Systems and methods for dynamic time division duplex adjustment in a wireless network

ABSTRACT

A system described herein may identify Quality of Service (“QoS”) information associated with a User Equipment (“UE”) that is connected to a radio access network (“RAN”) of a wireless network. The QoS information may include or may be based on a network slice identifier, a QoS value, a Service Level Agreement (“SLA”), a model associated with UE attributes, or other suitable information. The system may determine a time division duplex (“TDD”) configuration for the UE based on the identified QoS information and/or models that associate UE attributes to TDD configurations. The system may implement the determined TDD configuration at the RAN. The UE and the RAN may communicate with each other according to the implemented TDD configuration, which may include particular timing information for uplink and downlink communications between the UE and the RAN.

BACKGROUND

Wireless networks, such as radio access networks (“RANs”), may usevarious techniques for allocating physical radio frequency (“RF”)resources for communications to and from User Equipment (“UEs”), such aswireless phones, Internet of Things (“IoT”) devices, fixed wirelessaccess (“FWA”) devices, or other types of devices. One such techniquemay include time division duplex (“TDD”), in which the same portion ofRF spectrum is used for uplink transmissions during a first time periodand for downlink transmissions during a second time period.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example overview of one or more embodimentsdescribed herein;

FIG. 2 illustrates an example arrangement of physical resourcesassociated with a RAN in the time and frequency domains;

FIG. 3 illustrates an example TDD configuration associated with a givenUE;

FIG. 4 illustrates examples of different TDD configurations associatedwith different UEs, in accordance with some embodiments;

FIG. 5 illustrates an example mapping between Quality of Service (“QoS”)identifiers and TDD configurations, in accordance with some embodiments;

FIG. 6 illustrates an example association between UE models and TDDconfigurations, in accordance with some embodiments;

FIG. 7 illustrates an example of implementing a TDD configuration basedon session QoS parameters provided by a core network, in accordance withsome embodiments;

FIG. 8 illustrates an example process for implementing a TDDconfiguration for a particular UE based on attributes of the UE and/orQoS information associated with the UE, in accordance with someembodiments;

FIG. 9 illustrates an example environment in which one or moreembodiments, described herein, may be implemented;

FIG. 10 illustrates an example arrangement of a RAN, in accordance withsome embodiments;

FIG. 11 illustrates an example arrangement of an Open RAN (“O-RAN”)environment in which one or more embodiments, described herein, may beimplemented; and

FIG. 12 illustrates example components of one or more devices, inaccordance with one or more embodiments described herein.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

Embodiments described herein provide for the dynamic adjustment of TDDparameters in a wireless network. Such adjustment may, in someembodiments, include adjusting the duration, arrangement, or otherattributes of uplink and/or downlink time windows associated with one ormore wireless channels between a UE and a RAN. For example, suchadjustment may include increasing a ratio of downlink resources touplink resources (e.g., increasing an amount of time that a particularportion of RF spectrum is allocated to downlink communications relativeto an amount of time that the particular portion of RF spectrum isallocated to uplink communications), or vice versa.

As discussed herein, the adjustments may be made based on varyingcriteria, such as a network slice associated with a communicationsession between a UE and a core network, attributes of the UE (e.g.,device type, UE power class, etc.), location of the UE and/or the RAN,QoS thresholds or Service Level Agreements (“SLAs”) associated with theUE, and/or other suitable criteria. In some embodiments, such criteriamay be modeled using modeling techniques such as artificialintelligence/machine learning (“AI/ML”) techniques or other suitabletechniques, and may be predictively or proactively applied tocommunication channels between one or more UEs and one or more RANs.

Modifying TDD parameters associated with a particular UE may allow forfine tuning, adjusting, etc. of a communication channel between the UEand the RAN, in order to enhance utilization of RF resources of the RAN(e.g., increase the usage of allocated resources and decrease the amountof resources that are unallocated but not used to carry traffic).Further embodiments described herein may increase the performance ofcommunications between the UE and the RAN by minimizing an amount ofqueueing delay. As such, the user experience of users of UEs may beimproved, as the perceived performance of traffic associated with the UEmay be improved. Further, the adjustment of TDD parameters for a UE mayallow for the adjustment of a resource allocation associated with the UEwithout needing to modify the resource allocation associated with otherUEs that are communicatively coupled to the same RAN, thus allowing forgranular control of resource allocations on a per-UE or per-UE groupbasis.

As shown in FIG. 1 , UE 101 may be communicatively coupled to basestation 103. For example, UE 101 and base station 103 may have performedthe establishment of one or more RF channels, such as be performing aRadio Resource Control (“RRC”) setup procedure or other suitableprocedure. Base station 103 may be one out of a set of base stationsassociated with a RAN of a wireless network.

UE 101 may include a wireless phone, an IoT device, a Machine-to-Machine(“M2M”) device, an FWA device, or other suitable type of device thatcommunicates wirelessly with base station 103. Base station 103 may, forexample, serve as a wireless interface between UE 101 and one or morenetworks, such as core network 105, which may provide routing services,call or session management services, traffic processing services, orother services to UE 101. Core network 105 may be associated with one ormore network slices, where different slices provide differentiatedlevels of service, such as service in accordance with different QoSparameters.

UE 101 and core network 105 may accordingly be associated with one ormore sessions (established at 102), such as a protocol data unit (“PDU”)session, a user plane data session, an Internet Protocol (“IP”) session,or other type of communication session. Such communication sessions maybe used to carry voice traffic between UE 101 and core network 105,application traffic, data traffic, and/or other types of traffic. Corenetwork 105 may, for example, route such traffic between UE 101 and oneor more other networks or application servers. The communication sessionor sessions may be associated with one or more network slices, SLAs, QoSparameters, Access Point Names (“APNs”), or the like, which may indicateparticular performance metrics, thresholds, goals, etc. (e.g., minimumacceptable throughput, maximum acceptable latency, etc.) for the one ormore sessions.

In accordance with some embodiments, QoS Determination System (“QDS”)107 may identify the establishment (at 102) of one or more communicationsessions between UE 101 and core network 105. In some embodiments, QDS107 may be, may be implemented by, and/or may be communicatively coupledto one or more elements of core network 105, such as a SessionManagement Function (“SMF”), a User Plane Function (“UPF”), a PolicyControl Function (“PCF”), or the like. Additionally, or alternatively,QDS 107 may be external to core network 105, and may receive anindication of the session establishment (at 102) from a Network ExposureFunction (“NEF”), a Service Capability Exposure Function (“SCEF”), orother interface associated with core network 105. In some embodiments,the information regarding the one or more communication sessions mayinclude an indication of QoS thresholds, SLAs, network slices, etc. withwhich the one or more communication sessions are associated. Suchindications may include an index or reference to a mapping of QoSthresholds, SLAs, etc. In some embodiments, such index or reference mayinclude a Network Slice Selection Assistance Information (“NSSAI”)value, a Fifth Generation (“5G”) QoS identifier (“5QI”) value, or othersuitable value.

In some embodiments, QDS 107 may receive information regarding UE 101from a Unified Data Management function (“UDM”), a Home SubscriberServer (“HSS”), or some other device or system that maintainsinformation regarding UE 101. Such UE information may include a devicetype of UE 101 (e.g., mobile telephone, IoT device, M2M device, etc.),attributes of UE 101 (e.g., UE power class, battery level, processorspeed, etc.), slice authorization information (e.g., an indication ofnetwork slices that UE 101 is authorized to access), SLA information(e.g., indicating one or more SLAs, QoS thresholds, etc.), or othersuitable UE information.

QDS 107 may determine (at 104) QoS parameters for UE 101 and/or for theone or more sessions associated with UE 101 and core network 105. Forexample, QDS 107 may determine such QoS parameters based on informationregarding the communication session and/or UE 101, as discussed above.The QoS parameters may include and/or may be based on performancethresholds, traffic or application type (e.g., voice traffic, contentstreaming traffic, etc.), or other suitable parameters. In someembodiments, as described further below, QDS 107 may maintain one ormore models, mappings, etc. based on which a particular set of QoSparameters may be determined (at 104) based on UE information, networkslice information, session information, or other suitable information.

QDS 107 may provide (at 106) the determined QoS parameters for thesession and/or for UE 101 to TDD Configuration System (“TCS”) 109. TCS109 may be communicatively coupled to base station 103. For example, thesame set of hardware may implement some or all of base station 103and/or TCS 109. Additionally, or alternatively, TCS 109 may implementedby a Multi-Access/Mobile Edge Computing (“MEC”) device, referred tosometimes herein simply as a “MEC,” that is communicatively coupled toor otherwise associated with base station 103. In some embodiments, QDS107 and TCS 109 may communicate via core network 105 and/or some othernetwork, application programming interface (“API”), or other suitablecommunication pathway.

In some embodiments, TCS 109 may receive or maintain a TDD configurationassociated with base station 103. For example, base station 103 maydetermine or maintain information indicating a resource allocationassociated with base station 103, which may include one or more TDDconfigurations. FIGS. 2 and 3 illustrate example resource allocationsand/or TDD configurations. As shown in FIG. 2 , RF resources of basestation 103 may be allocated on a time and frequency domain. Forexample, time slots 201 may repeat cyclically, and may each include aset of symbols 203, which may be orthogonal frequency-divisionmultiplexing (“OFDM”) symbols. In some embodiments, time slots 201 mayeach be 10-millisecond time periods or time periods of some otherduration. A particular symbol 203 may refer to a particular portion of aparticular slot 201. In this example, three example slots 201-1, 201-2,and 201-3 may each be associated with the same quantity of symbols 203(e.g., 14 symbols 203). A particular portion of the RF spectrum (e.g.,band, sub-band, carrier, sub-carrier, frequency range, etc.) may be ableto be allocated at each symbol. A particular portion of the RF spectrum,at a particular symbol 203, may be referred to as a Resource Element(“RE”) 205. In an example where base station 103 sends and/or receivesRF signals within 8 portions of the RF spectrum (e.g., carriers,sub-carriers, etc.), a particular slot 201 that includes 12 symbols 203may include 96 REs 205 that may be allocated to one or more UEs 101 thatare connected to base station 103. In some embodiments, base station 103may operate additional or fewer portions of the RF spectrum, and/or mayimplement slots 201 to include additional or fewer symbols 203.

One or more UEs 101 may thus be allocated a portion of the RF resourcesavailable with respect to a given base station 103, which may include aparticular set of REs 205 available during one or more slots 201. Asshown in FIG. 3 , for example, the allocation for a particular UE 101may include 10 REs. In some embodiments, a TDD configuration for UE 101may be used to indicate which REs are dedicated to uplink signals (e.g.,RF signals sent from UE 101 to base station 103) and which REs arededicated to downlink signals (e.g., RF signals sent from base station103 to UE 101).

REs 205 dedicated to uplink signals are denoted with a “U” in thefigure, while REs 205 dedicated to downlink signals are denoted with a“D” in the figure. Base station 103 may receive or “listen” for signalsfrom UE 101 on uplink REs, while UE 101 may receive or “listen” forsignals from base station 103 from base station 103 on downlink REs. Insome embodiments, the REs of a particular symbol 203 (e.g., portion ofslot 201 on the time domain) may be required to have the same TDDdedication (e.g., all REs 205 on the particular symbol 203 may berequired to be uplink or downlink REs). In some embodiments, REs 205 onthe same symbol 203 may be able to be a mix of uplink and downlink REs.In some embodiments, one or more REs 205 may be denoted as “guard” REs,“reserved” REs, and/or may be denoted in some manner other than “uplink”or “downlink.” Concepts described herein, with respect to uplink ordownlink REs, may be used in conjunction with embodiments in which REsmay be denoted in some other manner.

In this example, UE 101 may be associated with a 30/70 split of downlinkand uplink REs 205. As shown, for instance, the TDD configuration for UE101 may include, on slot 201, 3 downlink REs 205 and 7 uplink REs 205.In accordance with embodiments described herein, the TDD configurationfor UE 101 may be dynamically modified, without changing the REallocation for UE 101. For example, as discussed herein, the TDDconfiguration may be modified to a 50/50 split of downlink and uplinkREs 205, a 70/30 split, and/or some other split. Such modification may,in some embodiments, be made without modifying the quantity of REs 205allocated to UE 101 (or other UEs) within slot 201.

As such, different UEs 101 that are connected to base station 103 may beassociated with different respective resource allocations and differentTDD configurations. As shown in FIG. 4 , for example, resources of agiven base station 103 within a given slot 201 may be allocated to UEs101-1 through 101-5. UE 101-1 may, for example, be associated with afirst RE allocation and a first TDD configuration, UE 101-2 may beassociated with a second RE allocation and a second TDD configuration,UE 101-3 may be associated with a third RE allocation and a third TDDconfiguration, and so on. In some situations, a portion of the resourcesof base station 103 may be unallocated.

Returning to FIG. 1 , TCS 109 may determine (at 108) a TDD configurationfor UE 101 based on the QoS parameters received (at 106) from QDS 107.For example, TCS 109 may determine the TDD configuration based on UEattributes, session parameters, network slice, etc., discussed above. Asone example, TCS 109 may determine the TDD configuration based on amapping between session QoS parameters and TDD configurations. As shownin FIG. 5 , for example, TCS 109 may maintain data structure 501, whichmay include a mapping between 5QI values and TDD configurations. Datastructure 501 may indicate, for example, that if a communication sessionbetween UE 101 is associated with a 5QI value of 1, the TDDconfiguration for UE 101 should be allocated as a 50/50 split betweenuplink and downlink REs. Data structure 501 may further indicate that ifa communication session between UE 101 is associated with a 5QI value of2, the TDD configuration for UE 101 should be allocated as a 40/60 splitbetween uplink and downlink REs, that if a communication session betweenUE 101 is associated with a 5QI value of 3, the TDD configuration for UE101 should be allocated as a 30/70 split between uplink and downlinkREs, that if a communication session between UE 101 is associated with a5QI value of 4, the TDD configuration for UE 101 should be allocated asa 5/95 split between uplink and downlink REs, and so on.

Additionally, or alternatively, as shown in FIG. 6 , TCS 109 maygenerate, maintain, and/or refine one or more UE and/or QoS models 601(referred to herein simply as “models 601” for the sake of brevity) thatare associated with one or more TDD configurations 613. For example, asshown in FIG. 6 , models 601-1, 601-2, and 60-3 may be associated with afirst TDD configuration 613-1, model 601-4 may be associated with asecond TDD configuration 613-2, and model 601-5 may be associated with athird TDD configuration 613-3. TDD configurations 613 may indicate aratio, split, etc. of uplink and downlink RE allocations. Additionally,or alternatively, TDD configurations 613 may specify a minimum quantityof uplink and/or downlink REs in a given slot, a maximum quantity ofuplink and/or downlink REs in a given slot, a particular sequence orpattern of uplink and/or downlink REs, and/or some other type of TDDconfiguration parameters.

As further shown, models 601 may be associated with parameters and/orattributes, such as UE type 603, UE power class 605, UE location 607,slice (or other type of SLA or QoS level) identifier 609, time 611,and/or other types of parameters or attributes. As noted above, theparameters and/or attributes may be received by TCS 109 from one or moreelements of network 105, such as an SMF, a PCF, a UDM, and/or some othersuitable source.

UE type 603 may include, for example, an indication of a type of aparticular UE 101, such as a mobile telephone, an IoT device, an M2Mdevice, etc. In some embodiments, the type of UE 101 may include a makeor model of UE 101 and/or physical attributes or capabilities of UE 101,such as a screen size, processor speed, etc. UE power class 605 mayindicate an amount of power associated with wireless transmissionsassociated with one or more wireless radios of UE 101 and/or mayotherwise be based on the capability of UE 101 to send and/or receivewireless signals to and/or from base station 103.

UE location 607 may include a geographical location of UE 101 asdetermined by UE 101 (e.g., using Global Positioning System (“GPS”)techniques or other suitable techniques) and/or by one or more basestations 103 utilizing a wireless triangulation technique or othersuitable technique. UE location 607 may include latitude and longitudecoordinates, GPS coordinates, an address, a name of a city or other typeof region, and/or other type of indication of a geographical location ofUE 101.

Slice, SLA, QoS, etc. identifiers 609 may include one or moreidentifiers of one or more network slices, SLAs, QoS levels, etc.associated with UE 101. For example, such identifiers 609 may include alist of network slices that UE 101 is authorized to access.Additionally, or alternatively, identifiers 609 may include anidentifier (e.g., a NSSAI value or other identifier) of a particularnetwork slice that is actively being used for one or more communicationsessions between UE 101 and core network 105. In some embodiments,identifiers 609 may include a 5QI value associated with one or morecommunication sessions (e.g., one or more PDU sessions) between UE 101and core network 105. In some embodiments, identifiers 609 may includean APN associated with one or more communication sessions between UE 101and core network 105.

Thus, identifiers 609 may include identifiers or other indications ofnetwork slices, SLAs, QoS levels, etc. that are associated with UE 101.For example, in situations where UE 101 is engaged in multiple sessionswith 105, where each session is associated with a different networkslice, SLA, etc., identifiers 609 may include identifiers of eachdifferent network slice, SLA, etc. In this manner, the same UE 101 maybe associated with different TDD configurations 613 when engaging indifferent combinations of types of communication sessions with corenetwork 105. For example, when engaging in a voice call, UE 101 may beassociated with a first model 601-1 (and therefore with TDDconfiguration 613-1), while the same UE 101 may be associated withanother model 601-4 (and therefore with TDD configuration 613-2) whenengaging in a voice call and a file transfer.

Time 611 may refer to time of day, day of week, and/or other temporalcharacteristics. For example, during working hours (e.g., 9 AM-5 PM), UE101 may be associated with the first model 601-1 (and therefore with TDDconfiguration 613-1), while the same UE 101 may be associated with theother model 601-4 (and therefore with TDD configuration 613-2) duringnon-working hours (e.g., 5 PM-9 AM).

In some embodiments, TCS 109 may refine models 601, TDD configurations613, and/or respective correlations or associations between models 601and TDD configurations 613 using AI/ML techniques or other suitabletechniques. For example, TCS 109 may iteratively refine models 601, TDDconfigurations 613, and/or the correlations/associations between models601 and TDD configurations 613 in order to determine an optimal TDDconfiguration 613 when given a UE 101 having particular attributes, orlocated in a particular location and/or at a particular time.

In some embodiments, model 601 may include additional and/or differentinformation. For example, in some embodiments, model 601 may includeidentifiers of groups, categories, etc. of UEs 101. For example, aparticular group of UEs 101 may include UEs 101 belonging to aparticular organization or institution, may be associated with aparticular access class (e.g., “first responders” or “fleet vehicles”),etc. In this manner, different models 601 may be applied to differentgroups, categories, etc. of UEs 101.

Returning to FIG. 1 , TCS 109 may provide (at 110) the determined TDDconfiguration for UE 101 to base station 103. Base station 103 mayprovide (at 112) the TDD configuration to UE 101. For example, basestation 103 may provide the TDD configuration to UE 101 as an RRCmessage (e.g., RRC Reconfiguration Request message), as a SystemInformation Block (“SIB”), and/or in some other suitable manner. Asnoted above, the TDD configuration may include timing information, suchas times within slots 201 that UE 101 is able to output uplink trafficto base station 103 and/or receive downlink traffic from base station103.

Base station 103 and UE 101 may accordingly communicate (at 114) witheach other according to the TDD configuration provided (at 110) by TCS109. For example, UE 101 may output uplink traffic to base station 103on REs dedicated to uplink traffic from UE 101, and UE 101 may receivedownlink traffic from base station 103 on REs dedicated to downlinktraffic to UE 101.

FIG. 7 illustrates an example of determining or adjusting TDDconfiguration parameters based on information provided by one or moreelements of core network 105, such as SMF 701. In some embodiments, UE101 and/or base station 103 may communicate with SMF 701 via one or moreother network elements, such as an AMF. UE 101 and SMF 701 (e.g., via anAMF or other suitable network element) may participate (at 702) in asession establishment procedure, such as a PDU session establishmentprocedure. The PDU session may include, for example, a user plane datasession between UE 101 and one or more elements of the network, such asa UPF.

As part of such procedure, or otherwise based on the sessionestablishment, SMF 701 may determine (at 704) QoS parameters for thecommunication session associated with UE 101 (e.g., between UE 101 andthe UPF). SMF 701 may, for example, receive UE information from a UDM,may receive policy information from a PCF, and/or may receive othersuitable information based on which SMF 701 may determine the QoSparameters associated with the session. In some embodiments, suchparameters include a slice identifier, a 5QI, an APN, or other suitableQoS parameters or identifiers.

SMF 701 may provide (at 706) the QoS parameters associated with thesession to base station 103. For example, in some embodiments, SMF 701may provide information associated with the session (e.g., endpointidentifiers, session identifier, etc.), which may include the QoSparameters, to an AMF via an N11 interface. The AMF may output suchinformation to base station 103 via an N2 interface.

As similarly discussed above, TCS 109 may determine (at 710) a TDDconfiguration for UE 101 based on the QoS parameters provided (at 706)by SMF 701, which may include a 5QI value, a slice identifier, and/orsome other suitable value or identifier. TCS 109 may provide (at 712)the TDD configuration to base station 103, which may forward (at 714)the TDD configuration to UE 101. UE 101 and base station 103 may proceedto communicate (at 716) with each other according to the TDDconfiguration, which may include sending and receiving traffic at timescorresponding to the TDD configuration.

FIG. 8 illustrates an example process 800 for implementing a TDDconfiguration for a particular UE 101 based on attributes of UE 101and/or QoS information associated with UE 101. In some embodiments, someor all of process 800 may be performed by TCS 109. In some embodiments,one or more other devices may perform some or all of process 800 inconcert with TCS 109, such as QDS 107.

As shown, process 800 may include generating and/or refining (at 802)one or more UE models and associations between UE models and respectiveTDD configurations. For example, as discussed above with respect to FIG.6 , TCS 109 may generate and/or refine models 601 and/or TDDconfigurations 613 over time using modeling techniques such as AI/MLtechniques or other suitable techniques, in order to optimizeperformance, network efficiency, and/or other suitable metrics,objectives, and/or measures of yield. As such, given a set of inputparameters (e.g., UE type, UE power class, UE location, network sliceassociated with a given UE 101 and/or a communication session associatedwith UE 101, etc.), a particular TDD configuration 613 may be identifiedas optimal or otherwise associated with such set of input parameters.

Process 800 may further include identifying (at 804) QoS informationand/or a particular model 601 associated with a particular UE 101connected to a RAN (e.g., a particular base station 103 of the RAN). Forexample, TCS 109 may receive information indicating a network sliceassociated with UE 101 and/or a communication session between UE 101 andcore network 105, a QoS identifier (e.g., a 5QI value or some other QoSidentifier) associated with UE 101 and/or a communication sessionbetween UE 101 and core network 105, and/or other suitable QoSinformation. Additionally, or alternatively, TCS 109 may identify aparticular model 601 associated with UE 101 and/or the communicationsession, based on attributes of UE 101 and/or the communication session(e.g., UE type 603, UE power class 605, UE location 607, network sliceand/or SLA identifier 609, current time 611, etc.).

Process 800 may additionally include determining (at 806) a TDDconfiguration for UE 101 based on the QoS information and/or model 601.For example, as discussed above with respect to FIG. 5 , TCS 109 mayidentify a mapping between QoS identifiers and TDD configurations.Additionally, or alternatively, TCS 109 may identify an associationbetween a particular model 601 (e.g., with which UE 101 is associated)and a particular TDD configuration 613.

Process 800 may also include implementing (at 808) the TDD configurationat the RAN. For example, TCS 109 may provide information indicating thedetermined (at 806) TDD configuration to base station 103, which maycommunicate with UE 101 according to the TDD configuration (e.g., mayutilize particular times, symbols, and/or REs for uplink or downlinkcommunications, as indicated in the TDD configuration) between UE 101and base station 103. Base station 103 may provide the TDD configurationto UE 101, such that UE 101 and base station 103 are synchronized withrespect to the TDD configuration. In some embodiments, base station 103may further modify the received TDD configuration before implementingthe TDD configuration (e.g., the TDD configuration may be used by basestation 103 as a factor in ultimately determining a TDD configuration toimplement with respect to UE 101).

FIG. 9 illustrates an example environment 900, in which one or moreembodiments may be implemented. In some embodiments, environment 900 maycorrespond to a 5G network, and/or may include elements of a 5G network.In some embodiments, environment 900 may correspond to a 5GNon-Standalone (“NSA”) architecture, in which a 5G radio accesstechnology (“RAT”) may be used in conjunction with one or more otherRATs (e.g., a Long-Term Evolution (“LTE”) RAT), and/or in which elementsof a 5G core network may be implemented by, may be communicativelycoupled with, and/or may include elements of another type of corenetwork (e.g., an evolved packet core (“EPC”)). As shown, environment900 may include UE 101, RAN 910 (which may include one or more NextGeneration Node Bs (“gNBs”) 911), RAN 912 (which may include one or moreevolved Node Bs (“eNBs”) 913), and various network functions such asAccess and Mobility Management Function (“AMF”) 915, Mobility ManagementEntity (“MME”) 916, Serving Gateway (“SGW”) 917, Session ManagementFunction (“SMF”)/Packet Data Network (“PDN”) Gateway (“PGW”)-Controlplane function (“PGW-C”) 920, Policy Control Function (“PCF”)/PolicyCharging and Rules Function (“PCRF”) 925, Application Function (“AF”)930, User Plane Function (“UPF”)/PGW-User plane function (“PGW-U”) 935,Home Subscriber Server (“HSS”)/Unified Data Management (“UDM”) 940, andAuthentication Server Function (“AUSF”) 945. Environment 900 may alsoinclude one or more networks, such as Data Network (“DN”) 950.Environment 900 may include one or more additional devices or systemscommunicatively coupled to one or more networks (e.g., DN 950), such asQDS 107 and/or TCS 109.

The example shown in FIG. 9 illustrates one instance of each networkcomponent or function (e.g., one instance of SMF/PGW-C 920, PCF/PCRF925, UPF/PGW-U 935, HSS/UDM 940, and/or AUSF 945). In practice,environment 900 may include multiple instances of such components orfunctions. For example, in some embodiments, environment 900 may includemultiple “slices” of a core network, where each slice includes adiscrete set of network functions (e.g., one slice may include a firstinstance of SMF/PGW-C 920, PCF/PCRF 925, UPF/PGW-U 935, HSS/UDM 940,and/or AUSF 945, while another slice may include a second instance ofSMF/PGW-C 920, PCF/PCRF 925, UPF/PGW-U 935, HSS/UDM 940, and/or AUSF945). The different slices may provide differentiated levels of service,such as service in accordance with different QoS parameters.

The quantity of devices and/or networks, illustrated in FIG. 9 , isprovided for explanatory purposes only. In practice, environment 900 mayinclude additional devices and/or networks, fewer devices and/ornetworks, different devices and/or networks, or differently arrangeddevices and/or networks than illustrated in FIG. 9 . For example, whilenot shown, environment 900 may include devices that facilitate or enablecommunication between various components shown in environment 900, suchas routers, modems, gateways, switches, hubs, etc. Alternatively, oradditionally, one or more of the devices of environment 900 may performone or more network functions described as being performed by anotherone or more of the devices of environment 900. Devices of environment900 may interconnect with each other and/or other devices via wiredconnections, wireless connections, or a combination of wired andwireless connections. In some implementations, one or more devices ofenvironment 900 may be physically integrated in, and/or may bephysically attached to, one or more other devices of environment 900.

UE 101 may include a computation and communication device, such as awireless mobile communication device that is capable of communicatingwith RAN 910, RAN 912, and/or DN 950. UE 101 may be, or may include, aradiotelephone, a personal communications system (“PCS”) terminal (e.g.,a device that combines a cellular radiotelephone with data processingand data communications capabilities), a personal digital assistant(“PDA”) (e.g., a device that may include a radiotelephone, a pager,Internet/intranet access, etc.), a smart phone, a laptop computer, atablet computer, a camera, a personal gaming system, an IoT device(e.g., a sensor, a smart home appliance, a wearable device, an M2Mdevice, or the like), or another type of mobile computation andcommunication device. UE 101 may send traffic to and/or receive traffic(e.g., user plane traffic) from DN 950 via RAN 910, RAN 912, and/orUPF/PGW-U 935.

RAN 910 may be, or may include, a 5G RAN that includes one or more basestations (e.g., one or more gNBs 911), via which UE 101 may communicatewith one or more other elements of environment 900. UE 101 maycommunicate with RAN 910 via an air interface (e.g., as provided by gNB911). For instance, RAN 910 may receive traffic (e.g., voice calltraffic, data traffic, messaging traffic, signaling traffic, etc.) fromUE 101 via the air interface, and may communicate the traffic toUPF/PGW-U 935, and/or one or more other devices or networks. Similarly,RAN 910 may receive traffic intended for UE 101 (e.g., from UPF/PGW-U935, AMF 915, and/or one or more other devices or networks) and maycommunicate the traffic to UE 101 via the air interface. In someembodiments, base station 103 may be, may include, and/or may beimplemented by one or more gNBs 911.

RAN 912 may be, or may include, a LTE RAN that includes one or more basestations (e.g., one or more eNBs 913), via which UE 101 may communicatewith one or more other elements of environment 900. UE 101 maycommunicate with RAN 912 via an air interface (e.g., as provided by eNB913). For instance, RAN 910 may receive traffic (e.g., voice calltraffic, data traffic, messaging traffic, signaling traffic, etc.) fromUE 101 via the air interface, and may communicate the traffic toUPF/PGW-U 935, and/or one or more other devices or networks. Similarly,RAN 910 may receive traffic intended for UE 101 (e.g., from UPF/PGW-U935, SGW 917, and/or one or more other devices or networks) and maycommunicate the traffic to UE 101 via the air interface. In someembodiments, base station 103 may be, may include, and/or may beimplemented by one or more eNBs 913.

AMF 915 may include one or more devices, systems, Virtualized NetworkFunctions (“VNFs”), Cloud-Native Network Functions (“CNFs”), etc., thatperform operations to register UE 101 with the 5G network, to establishbearer channels associated with a session with UE 101, to hand off UE101 from the 5G network to another network, to hand off UE 101 from theother network to the 5G network, manage mobility of UE 101 between RANs910 and/or gNBs 911, and/or to perform other operations. In someembodiments, the 5G network may include multiple AMFs 915, whichcommunicate with each other via the N14 interface (denoted in FIG. 9 bythe line marked “N14” originating and terminating at AMF 915).

MME 916 may include one or more devices, systems, VNFs, CNFs, etc., thatperform operations to register UE 101 with the EPC, to establish bearerchannels associated with a session with UE 101, to hand off UE 101 fromthe EPC to another network, to hand off UE 101 from another network tothe EPC, manage mobility of UE 101 between RANs 912 and/or eNBs 913,and/or to perform other operations.

SGW 917 may include one or more devices, systems, VNFs, CNFs, etc., thataggregate traffic received from one or more eNBs 913 and send theaggregated traffic to an external network or device via UPF/PGW-U 935.Additionally, SGW 917 may aggregate traffic received from one or moreUPF/PGW-Us 935 and may send the aggregated traffic to one or more eNBs913. SGW 917 may operate as an anchor for the user plane duringinter-eNB handovers and as an anchor for mobility between differenttelecommunication networks or RANs (e.g., RANs 910 and 912).

SMF/PGW-C 920 may include one or more devices, systems, VNFs, CNFs,etc., that gather, process, store, and/or provide information in amanner described herein. SMF/PGW-C 920 may, for example, facilitate theestablishment of communication sessions on behalf of UE 101. In someembodiments, the establishment of communications sessions may beperformed in accordance with one or more policies provided by PCF/PCRF925. In some embodiments, SMF/PGW-C 920 may include, may implement, maybe communicatively coupled to, and/or may otherwise be associated withSMF 701.

PCF/PCRF 925 may include one or more devices, systems, VNFs, CNFs, etc.,that aggregate information to and from the 5G network and/or othersources. PCF/PCRF 925 may receive information regarding policies and/orsubscriptions from one or more sources, such as subscriber databasesand/or from one or more users (such as, for example, an administratorassociated with PCF/PCRF 925).

AF 930 may include one or more devices, systems, VNFs, CNFs, etc., thatreceive, store, and/or provide information that may be used indetermining parameters (e.g., quality of service parameters, chargingparameters, or the like) for certain applications.

UPF/PGW-U 935 may include one or more devices, systems, VNFs, CNFs,etc., that receive, store, and/or provide data (e.g., user plane data).For example, UPF/PGW-U 935 may receive user plane data (e.g., voice calltraffic, data traffic, etc.), destined for UE 101, from DN 950, and mayforward the user plane data toward UE 101 (e.g., via RAN 910, SMF/PGW-C920, and/or one or more other devices). In some embodiments, multipleUPFs 935 may be deployed (e.g., in different geographical locations),and the delivery of content to UE 101 may be coordinated via the N9interface (e.g., as denoted in FIG. 9 by the line marked “N9”originating and terminating at UPF/PGW-U 935). Similarly, UPF/PGW-U 935may receive traffic from UE 101 (e.g., via RAN 910, SMF/PGW-C 920,and/or one or more other devices), and may forward the traffic toward DN950. In some embodiments, UPF/PGW-U 935 may communicate (e.g., via theN4 interface) with SMF/PGW-C 920, regarding user plane data processed byUPF/PGW-U 935.

HSS/UDM 940 and AUSF 945 may include one or more devices, systems, VNFs,CNFs, etc., that manage, update, and/or store, in one or more memorydevices associated with AUSF 945 and/or HSS/UDM 940, profile informationassociated with a subscriber. AUSF 945 and/or HSS/UDM 940 may performauthentication, authorization, and/or accounting operations associatedwith the subscriber and/or a communication session with UE 101.

DN 950 may include one or more wired and/or wireless networks. Forexample, DN 950 may include an Internet Protocol (“IP”)-based PDN, awide area network (“WAN”) such as the Internet, a private enterprisenetwork, and/or one or more other networks. UE 101 may communicate,through DN 950, with data servers, other UEs 101, and/or to otherservers or applications that are coupled to DN 950. DN 950 may beconnected to one or more other networks, such as a public switchedtelephone network (“PSTN”), a public land mobile network (“PLMN”),and/or another network. DN 950 may be connected to one or more devices,such as content providers, applications, web servers, and/or otherdevices, with which UE 101 may communicate.

FIG. 10 illustrates an example Distributed Unit (“DU”) network 1000,which may be included in and/or implemented by one or more RANs (e.g.,RAN 910, RAN 912, or some other RAN). In some embodiments, a particularRAN may include one DU network 1000. In some embodiments, a particularRAN may include multiple DU networks 1000. In some embodiments, DUnetwork 1000 may correspond to a particular gNB 911 of a 5G RAN (e.g.,RAN 910). In some embodiments, DU network 1000 may correspond tomultiple gNBs 911. In some embodiments, DU network 1000 may correspondto one or more other types of base stations of one or more other typesof RANs. As shown, DU network 1000 may include Central Unit (“CU”) 1005,one or more Distributed Units (“DUs”) 1003-1 through 1003-N (referred toindividually as “DU 1003,” or collectively as “DUs 1003”), and one ormore Radio Units (“RUs”) 1001-1 through 1001-M (referred to individuallyas “RU 1001,” or collectively as “RUs 1001”).

CU 1005 may communicate with a core of a wireless network (e.g., maycommunicate with one or more of the devices or systems described abovewith respect to FIG. 9 , such as AMF 915 and/or UPF/PGW-U 935). In theuplink direction (e.g., for traffic from UEs 101 to a core network), CU1005 may aggregate traffic from DUs 1003, and forward the aggregatedtraffic to the core network. In some embodiments, CU 1005 may receivetraffic according to a given protocol (e.g., Radio Link Control (“RLC”))from DUs 1003, and may perform higher-layer processing (e.g., mayaggregate/process RLC packets and generate Packet Data ConvergenceProtocol (“PDCP”) packets based on the RLC packets) on the trafficreceived from DUs 1003.

In accordance with some embodiments, CU 1005 may receive downlinktraffic (e.g., traffic from the core network) for a particular UE 101,and may determine which DU(s) 1003 should receive the downlink traffic.DU 1003 may include one or more devices that transmit traffic between acore network (e.g., via CU 1005) and UE 101 (e.g., via a respective RU1001). DU 1003 may, for example, receive traffic from RU 1001 at a firstlayer (e.g., physical (“PHY”) layer traffic, or lower PHY layertraffic), and may process/aggregate the traffic to a second layer (e.g.,upper PHY and/or RLC). DU 1003 may receive traffic from CU 1005 at thesecond layer, may process the traffic to the first layer, and providethe processed traffic to a respective RU 1001 for transmission to UE101.

RU 1001 may include hardware circuitry (e.g., one or more RFtransceivers, antennas, radios, and/or other suitable hardware) tocommunicate wirelessly (e.g., via an RF interface) with one or more UEs101, one or more other DUs 1003 (e.g., via RUs 1001 associated with DUs1003), and/or any other suitable type of device. In the uplinkdirection, RU 1001 may receive traffic from UE 101 and/or another DU1003 via the RF interface and may provide the traffic to DU 1003. In thedownlink direction, RU 1001 may receive traffic from DU 1003, and mayprovide the traffic to UE 101 and/or another DU 1003.

RUs 1001 may, in some embodiments, be communicatively coupled to one ormore Multi-Access/Mobile Edge Computing (“MEC”) devices, referred tosometimes herein simply as “MECs” 1007. For example, RU 1001-1 may becommunicatively coupled to MEC 1007-1, RU 1001-M may be communicativelycoupled to MEC 1007-M, DU 1003-1 may be communicatively coupled to MEC1007-2, DU 1003-N may be communicatively coupled to MEC 1007-N, CU 1005may be communicatively coupled to MEC 1007-3, and so on. MECs 1007 mayinclude hardware resources (e.g., configurable or provisionable hardwareresources) that may be configured to provide services and/or otherwiseprocess traffic to and/or from UE 101, via a respective RU 1001.

For example, RU 1001-1 may route some traffic, from UE 101, to MEC1007-1 instead of to a core network (e.g., via DU 1003 and CU 1005). MEC1007-1 may process the traffic, perform one or more computations basedon the received traffic, and may provide traffic to UE 101 via RU1001-1. In this manner, ultra-low latency services may be provided to UE101, as traffic does not need to traverse DU 1003, CU 1005, and anintervening backhaul network between DU network 1000 and the corenetwork. In some embodiments, MEC 1007 may include, and/or mayimplement, some or all of the functionality described above with respectto QDS 107, TCS 109, UPF 935, and/or one or more other devices, systems,VNFs, CNFs, etc.

FIG. 11 illustrates an example O-RAN environment 1100, which maycorrespond to RAN 910, RAN 912, and/or DU network 1000. For example, RAN910, RAN 912, and/or DU network 1000 may include one or more instancesof O-RAN environment 1100, and/or one or more instances of O-RANenvironment 1100 may implement RAN 910, RAN 912, DU network 1000, and/orsome portion thereof. As shown, O-RAN environment 1100 may includeNon-Real Time Radio Intelligent Controller (“RIC”) 1101, Near-Real TimeRIC 1103, O-eNB 1105, O-CU-Control Plane (“O-CU-CP”) 1107, O-CU-UserPlane (“O-CU-UP”) 1109, O-DU 1111, O-RU 1113, and O-Cloud 1115. In someembodiments, O-RAN environment 1100 may include additional, fewer,different, and/or differently arranged components.

In some embodiments, some or all of the elements of O-RAN environment1100 may be implemented by one or more configurable or provisionableresources, such as virtual machines, cloud computing systems, physicalservers, and/or other types of configurable or provisionable resources.In some embodiments, some or all of O-RAN environment 1100 may beimplemented by, and/or communicatively coupled to, one or more MECs1007.

Non-Real Time RIC 1101 and Near-Real Time RIC 1103 may receiveperformance information (and/or other types of information) from one ormore sources, and may configure other elements of O-RAN environment 1100based on such performance or other information. For example, Near-RealTime RIC 1103 may receive performance information, via one or more E2interfaces, from O-eNB 1105, O-CU-CP 1107, and/or O-CU-UP 1109, and maymodify parameters associated with O-eNB 1105, O-CU-CP 1107, and/orO-CU-UP 1109 based on such performance information. In some embodiments,such parameters may include TDD configuration information, as discussedabove. For example, in some embodiments, Near-Real Time MC 1103 mayperform some or all of the functionality described above with respect toQDS 107 and/or TCS 109.

Non-Real Time RIC 1101 may receive performance information associatedwith O-eNB 1105, O-CU-CP 1107, O-CU-UP 1109, and/or one or more otherelements of O-RAN environment 1100 and may utilize machine learningand/or other higher level computing or processing to determinemodifications to the configuration of O-eNB 1105, O-CU-CP 1107, O-CU-UP1109, and/or other elements of O-RAN environment 1100. In someembodiments, Non-Real Time RIC 1101 may generate machine learning modelsbased on performance information associated with O-RAN environment 1100or other sources, and may provide such models to Near-Real Time RIC 1103for implementation.

O-eNB 1105 may perform functions similar to those described above withrespect to eNB 913. For example, O-eNB 1105 may facilitate wirelesscommunications between UE 101 and a core network. O-CU-CP 1107 mayperform control plane signaling to coordinate the aggregation and/ordistribution of traffic via one or more DUs 1003, which may includeand/or be implemented by one or more O-DUs 1111, and O-CU-UP 1109 mayperform the aggregation and/or distribution of traffic via such DUs 1003(e.g., O-DUs 1111). O-DU 1111 may be communicatively coupled to one ormore RUs 1001, which may include and/or may be implemented by one ormore O-RUs 1113. In some embodiments, O-Cloud 1115 may include or beimplemented by one or more MECs 1007, which may provide services, andmay be communicatively coupled, to O-CU-CP 1107, O-CU-UP 1109, O-DU1111, and/or O-RU 1113 (e.g., via an O1 and/or O2 interface).

FIG. 12 illustrates example components of device 1200. One or more ofthe devices described above may include one or more devices 1200. Device1200 may include bus 1210, processor 1220, memory 1230, input component1240, output component 1250, and communication interface 1260. Inanother implementation, device 1200 may include additional, fewer,different, or differently arranged components.

Bus 1210 may include one or more communication paths that permitcommunication among the components of device 1200. Processor 1220 mayinclude a processor, microprocessor, or processing logic that mayinterpret and execute instructions. In some embodiments, processor 1220may be or may include one or more hardware processors. Memory 1230 mayinclude any type of dynamic storage device that may store informationand instructions for execution by processor 1220, and/or any type ofnon-volatile storage device that may store information for use byprocessor 1220.

Input component 1240 may include a mechanism that permits an operator toinput information to device 1200 and/or other receives or detects inputfrom a source external to 1240, such as a touchpad, a touchscreen, akeyboard, a keypad, a button, a switch, a microphone or other audioinput component, etc. In some embodiments, input component 1240 mayinclude, or may be communicatively coupled to, one or more sensors, suchas a motion sensor (e.g., which may be or may include a gyroscope,accelerometer, or the like), a location sensor (e.g., a GlobalPositioning System (“GPS”)-based location sensor or some other suitabletype of location sensor or location determination component), athermometer, a barometer, and/or some other type of sensor. Outputcomponent 1250 may include a mechanism that outputs information to theoperator, such as a display, a speaker, one or more light emittingdiodes (“LEDs”), etc.

Communication interface 1260 may include any transceiver-like mechanismthat enables device 1200 to communicate with other devices and/orsystems. For example, communication interface 1260 may include anEthernet interface, an optical interface, a coaxial interface, or thelike. Communication interface 1260 may include a wireless communicationdevice, such as an infrared (“IR”) receiver, a Bluetooth® radio, or thelike. The wireless communication device may be coupled to an externaldevice, such as a remote control, a wireless keyboard, a mobiletelephone, etc. In some embodiments, device 1200 may include more thanone communication interface 1260. For instance, device 1200 may includean optical interface and an Ethernet interface.

Device 1200 may perform certain operations relating to one or moreprocesses described above. Device 1200 may perform these operations inresponse to processor 1220 executing software instructions stored in acomputer-readable medium, such as memory 1230. A computer-readablemedium may be defined as a non-transitory memory device. A memory devicemay include space within a single physical memory device or spreadacross multiple physical memory devices. The software instructions maybe read into memory 1230 from another computer-readable medium or fromanother device. The software instructions stored in memory 1230 maycause processor 1220 to perform processes described herein.Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes describedherein. Thus, implementations described herein are not limited to anyspecific combination of hardware circuitry and software.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit thepossible implementations to the precise form disclosed. Modificationsand variations are possible in light of the above disclosure or may beacquired from practice of the implementations.

For example, while series of blocks and/or signals have been describedabove (e.g., with regard to FIGS. 1-8 ), the order of the blocks and/orsignals may be modified in other implementations. Further, non-dependentblocks and/or signals may be performed in parallel. Additionally, whilethe figures have been described in the context of particular devicesperforming particular acts, in practice, one or more other devices mayperform some or all of these acts in lieu of, or in addition to, theabove-mentioned devices.

The actual software code or specialized control hardware used toimplement an embodiment is not limiting of the embodiment. Thus, theoperation and behavior of the embodiment has been described withoutreference to the specific software code, it being understood thatsoftware and control hardware may be designed based on the descriptionherein.

In the preceding specification, various example embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of the possible implementations. Infact, many of these features may be combined in ways not specificallyrecited in the claims and/or disclosed in the specification. Althougheach dependent claim listed below may directly depend on only one otherclaim, the disclosure of the possible implementations includes eachdependent claim in combination with every other claim in the claim set.

Further, while certain connections or devices are shown, in practice,additional, fewer, or different, connections or devices may be used.Furthermore, while various devices and networks are shown separately, inpractice, the functionality of multiple devices may be performed by asingle device, or the functionality of one device may be performed bymultiple devices. Further, multiple ones of the illustrated networks maybe included in a single network, or a particular network may includemultiple networks. Further, while some devices are shown ascommunicating with a network, some such devices may be incorporated, inwhole or in part, as a part of the network.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, groups or other entities, itshould be understood that such information shall be used in accordancewith all applicable laws concerning protection of personal information.Additionally, the collection, storage, and use of such information canbe subject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as can be appropriatefor the situation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various access control,encryption and anonymization techniques for particularly sensitiveinformation.

No element, act, or instruction used in the present application shouldbe construed as critical or essential unless explicitly described assuch. An instance of the use of the term “and,” as used herein, does notnecessarily preclude the interpretation that the phrase “and/or” wasintended in that instance. Similarly, an instance of the use of the term“or,” as used herein, does not necessarily preclude the interpretationthat the phrase “and/or” was intended in that instance. Also, as usedherein, the article “a” is intended to include one or more items, andmay be used interchangeably with the phrase “one or more.” Where onlyone item is intended, the terms “one,” “single,” “only,” or similarlanguage is used. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processorsconfigured to: identify Quality of Service (“QoS”) informationassociated with a User Equipment (“UE”) that is connected to a radioaccess network (“RAN”) of a wireless network; identify a power classassociated with the UE; determine a time division duplex (“TDD”)configuration for the UE based on the identified QoS information and theidentified power class associated with the UE; and implement thedetermined TDD configuration at the RAN, wherein the UE and the RANcommunicate with each other according to the implemented TDDconfiguration.
 2. The device of claim 1, wherein the QoS informationincludes a Fifth Generation (“5G”) QoS identifier (“5QI”) valueassociated with one or more communication sessions between the UE and acore of the wireless network.
 3. The device of claim 2, wherein the oneor more communication sessions include one or more protocol data unit(“PDU”) sessions.
 4. The device of claim 2, wherein the 5QI value isreceived from at least one of: a Session Management Function (“SMF”) ofthe core of the wireless network, or an Access and Mobility ManagementFunction (“AMF”) of the core of the wireless network.
 5. The device ofclaim 1, wherein the one or more processors are further configured to:maintain one or more models that correlate particular sets of UEattributes to particular TDD configurations; and select, based onattributes of the UE, a particular model of the one or more models,wherein determining the TDD configuration for the UE is further based onidentifying that the TDD configuration is associated with the particularmodel.
 6. The device of claim 5, wherein the attributes of the UEinclude at least one of: a UE device type, or the UE power class.
 7. Thedevice of claim 1, wherein the TDD configuration is a first TDDconfiguration and wherein the UE is a first UE, wherein the one or moreprocessors are further configured to: implement a second TDDconfiguration, that is different from the first TDD configuration, withrespect to a second UE that is communicatively coupled to the RAN.
 8. Anon-transitory computer-readable medium, storing a plurality ofprocessor-executable instructions to: identify Quality of Service(“QoS”) information associated with a User Equipment (“UE”) that isconnected to a radio access network (“RAN”) of a wireless network;identify a power class associated with the UE; determine a time divisionduplex (“TDD”) configuration for the UE based on the identified QoSinformation and the identified power class associated with the UE; andimplement the determined TDD configuration at the RAN, wherein the UEand the RAN communicate with each other according to the implemented TDDconfiguration.
 9. The non-transitory computer-readable medium of claim8, wherein the QoS information includes a Fifth Generation (“5G”) QoSidentifier (“5QI”) value associated with one or more communicationsessions between the UE and a core of the wireless network.
 10. Thenon-transitory computer-readable medium of claim 9, wherein the one ormore communication sessions include one or more protocol data unit(“PDU”) sessions.
 11. The non-transitory computer-readable medium ofclaim 9, wherein the 5QI value is received from at least one of: aSession Management Function (“SMF”) of the core of the wireless network,or an Access and Mobility Management Function (“AMF”) of the core of thewireless network.
 12. The non-transitory computer-readable medium ofclaim 8, wherein the plurality of processor-executable instructionsfurther include processor-executable instructions to: maintain one ormore models that correlate particular sets of UE attributes toparticular TDD configurations; and select, based on attributes of theUE, a particular model of the one or more models, wherein determiningthe TDD configuration for the UE is further based on identifying thatthe TDD configuration is associated with the particular model.
 13. Thenon-transitory computer-readable medium of claim 12, wherein theattributes of the UE include at least one of: a UE device type, or theUE power class.
 14. The non-transitory computer-readable medium of claim8, wherein the TDD configuration is a first TDD configuration andwherein the UE is a first UE, wherein the plurality ofprocessor-executable instructions further include processor-executableinstructions to: implement a second TDD configuration, that is differentfrom the first TDD configuration, with respect to a second UE that iscommunicatively coupled to the RAN.
 15. A method, comprising:identifying Quality of Service (“QoS”) information associated with aUser Equipment (“UE”) that is connected to a radio access network(“RAN”) of a wireless network; identifying a power class associated withthe UE; determining a time division duplex (“TDD”) configuration for theUE based on the identified QoS information and the identified powerclass associated with the UE; and implementing the determined TDDconfiguration at the RAN, wherein the UE and the RAN communicate witheach other according to the implemented TDD configuration.
 16. Themethod of claim 15, wherein the QoS information includes a FifthGeneration (“5G”) QoS identifier (“5QI”) value associated with one ormore communication sessions between the UE and a core of the wirelessnetwork.
 17. The method of claim 16, wherein the one or morecommunication sessions include one or more protocol data unit (“PDU”)sessions, and wherein the 5QI value is received from at least one of: aSession Management Function (“SMF”) of the core of the wireless network,or an Access and Mobility Management Function (“AMF”) of the core of thewireless network.
 18. The method of claim 15, further comprising:maintaining one or more models that correlate particular sets of UEattributes to particular TDD configurations; and selecting, based onattributes of the UE, a particular model of the one or more models,wherein determining the TDD configuration for the UE is further based onidentifying that the TDD configuration is associated with the particularmodel.
 19. The method of claim 18, wherein the attributes of the UEinclude at least one of: a UE device type, or the UE power class. 20.The method of claim 15, wherein the TDD configuration is a first TDDconfiguration and wherein the UE is a first UE, the method furthercomprising: implementing a second TDD configuration, that is differentfrom the first TDD configuration, with respect to a second UE that iscommunicatively coupled to the RAN.